This repository was archived by the owner on Jan 28, 2021. It is now read-only.
Corrected the high precision functions #90
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Apr 17, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Corrected the support functions for high precision positioning (UBX-NAV-HPPOSLLH).
Added four new functions:
which return the high resolution component of the lat, lon, height above ellipsoid and height above mean sea level as int8_t (8-bit signed char).
Updated ZED-F9P\Example8_GetHighPrecisionPositionAndAccuracy so it demonstrates how to use the new functions. The example cheats by printing the integer and fractional parts of the lat and lon as standard long integers to avoid having to use a 64-bit double (which is not supported on some platforms).
Enjoy!
Paul